feat(web): strengthen Observe release story#886
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 42 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
Comment |
|
|
@coderabbitai review |
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_ae6b56d7-a00c-4ced-b761-b8f972a3cb04) |
✅ Action performedReview finished.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
|
@coderabbitai review |
✅ Action performedReview finished.
|
1 participant
Note
Low Risk
Copy-only changes on a marketing page with no application logic, APIs, or auth.
Overview
Rewrites the Capgo Observe landing page (
observe.astro) marketing copy to emphasize post-rollout proof, release context, and a single workflow from deploy → health signals → Logs Insights.Hero and workflow rail now lead with when a release needs attention, clearer rollout-to-investigation narrative, and updated CTA/link text (See how Observe works).
Proof, reading, diagnose, CTA, and SEO bridge sections get new eyebrows, headlines, and body copy—shifting from feature-list tone to outcomes like ship with proof, start broad / narrow fast, and hand them the trail instead of only charts. Layout, data arrays (
proofPoints,screenSignals), and styling are unchanged in this diff.Reviewed by Cursor Bugbot for commit 92af9da. Bugbot is set up for automated code reviews on this repo. Configure here.